Chapter 7 Chinese Text Processing
In this chapter, we will turn to the topic of Chinese text processing. In particular, we will discuss one of the most important issues in Chinese language processing, i.e., word segmentation.
When we discuss English parts-of-speech tagging in Chapter 5, it is easy to do word tokenization in English because the word boundaries in English are more clearly delimited by whitespaces. Chinese, however, does not have whitespaces between characters, which leads to a serious problem for word tokenization.
We will look at the issues of word tokenization and talk about the most-often used library, jiebaR, for Chinese word segmentation. Also, we will include several case studies on Chinese text processing.
In later Chapter 9, we will introduce another segmenter developed by the CKIP Group at the Academia Sinica. The CKIP Tagger seems to be the state-of-art tagger for Taiwan Mandarin, i.e., with more additional functionalities.
library(tidyverse)
library(tidytext)
library(quanteda)
library(stringr)
library(jiebaR)
library(readtext)7.1 Chinese Word Segmenter jiebaR
7.1.1 Start
First, if you haven’t installed the library jiebaR, you may need to install it manually:
install.packages("jiebaR")
library("jiebaR")This is the version used for this tutorial.
packageVersion("jiebaR")## [1] '0.11'
Now let us take a look at a quick example. Let us assume that in our corpus, we have collected only one text document, with only a short paragraph.
text <- "綠黨桃園市議員王浩宇爆料,指民眾黨不分區被提名人蔡壁如、黃瀞瑩,在昨(6)日才請辭是為領年終獎金。台灣民眾黨主席、台北市長柯文哲7日受訪時則說,都是按流程走,不要把人家想得這麼壞。"There are two important steps in Chinese word segmentation:
- Initialize a
jiebarobject usingworker() - Tokenize the texts into words using the function
segment()with the designatedjiebarobject created earlier
seg1 <- worker()
segment(text, jiebar = seg1)## [1] "綠黨" "桃園市" "議員" "王浩宇" "爆料" "指民眾"
## [7] "黨" "不" "分區" "被" "提名" "人"
## [13] "蔡壁如" "黃" "瀞" "瑩" "在昨" "6"
## [19] "日" "才" "請辭" "是" "為領" "年終獎金"
## [25] "台灣民眾" "黨" "主席" "台北" "市長" "柯文"
## [31] "哲" "7" "日" "受訪" "時則" "說"
## [37] "都" "是" "按" "流程" "走" "不要"
## [43] "把" "人家" "想得" "這麼" "壞"
class(seg1)## [1] "jiebar" "segment" "jieba"
To word-tokenize the document, text, you first initialize a jiebar object, i.e., seg1, using worker() and feed this jiebar to segment(jiebar = seg1)and tokenize text into words.
7.1.2 Parameters Setting
There are many different parameters you can specify when you initialize the jiebar object. You may get more detail via the documentation ?worker. Some of the important arguments include:
user = ...: This argument is to specify the path to a user-defined dictionarystop_word = ...: This argument is to specify the path to a stopword listsymbol = FALSE: Whether to return symbols (the default is FALSE)bylines = FALSE: Whether to return a list or not (crucial if you are usingtidytext::unnest_tokens())
Exercise 7.1 In our earlier example, when we created the jiebar object named seg1, we did not specify any arguments for worker(). Can you tell what the default settings are for the parameters of worker()?
worker() with different settings (e.g., symbols = T, bylines = T) and see how the tokenization results differ from each other.
7.1.3 User-defined dictionary
From the above example, it is clear to see that some of the words are not correctly identified by the current segmenter: for example, 民眾黨, 不分區, 黃瀞瑩, 柯文哲.
It is always recommended to include a user-defined dictionary when tokenizing your texts because different corpora may have their own unique vocabulary (i.e., domain-specific lexicon).
This can be done with the argument user = ... when you initialize the jiebar object, i.e, worker(..., user = ...).
seg2 <- worker(user = "demo_data/dict-ch-user-demo.txt")
segment(text, seg2)## [1] "綠黨" "桃園市" "議員" "王浩宇" "爆料" "指"
## [7] "民眾黨" "不分區" "被" "提名" "人" "蔡壁如"
## [13] "黃瀞瑩" "在昨" "6" "日" "才" "請辭"
## [19] "是" "為領" "年終獎金" "台灣" "民眾黨" "主席"
## [25] "台北" "市長" "柯文哲" "7" "日" "受訪"
## [31] "時則" "說" "都" "是" "按" "流程"
## [37] "走" "不要" "把" "人家" "想得" "這麼"
## [43] "壞"
The format of the user-defined dictionary is a text file, with one word per line. Also, the default encoding of the dictionary is UTF-8.
Please note that in Windows, the default encoding of a Chinese txt file created by Notepad may not be UTF-8. (Usually, it is encoded in big-5.)
Creating a user-defined dictionary may take a lot of time. You may consult 搜狗詞庫, which includes many domain-specific dictionaries created by others.
However, it should be noted that the format of the dictionaries is .scel. You may need to convert the .scel to .txt before you use it in jiebaR.
To do the coversion automatically, please consult the library cidian.
Also, you need to do the traditional-simplified Chinese conversion as well. For this, you may consult the library ropencc in R.
7.1.4 Stopwords
When you initialize the jiebar, you can also specify a stopword list, i.e., words that you do not need to include in the later analyses.
For example, in text mining, functional words are usually less informative, thus often excluded in the process of preprocessing.
seg3 <- worker(user = "demo_data/dict-ch-user-demo.txt",
stop_word = "demo_data/stopwords-ch-demo.txt")
segment(text, seg3)## [1] "綠黨" "桃園市" "議員" "王浩宇" "爆料" "指"
## [7] "民眾黨" "不分區" "被" "提名" "人" "蔡壁如"
## [13] "黃瀞瑩" "在昨" "6" "才" "請辭" "為領"
## [19] "年終獎金" "台灣" "民眾黨" "主席" "台北" "市長"
## [25] "柯文哲" "7" "受訪" "時則" "說" "按"
## [31] "流程" "走" "不要" "把" "人家" "想得"
## [37] "這麼" "壞"
segment(text, seg2) were removed as compared to the results of segment(text, seg3)? (Note: seg2 and seg3 only differ in the stop_word=... argument.)
## [1] "日" "是" "都"
7.1.5 POS Tagging
So far we haven’t seen the parts-of-speech tags provided by the word segmenter. If you need the POS tags of the words, you need to specify the argument type = "tag" when you initialize the worker().
seg4 <- worker(type = "tag",
user = "demo_data/dict-ch-user-demo.txt",
stop_word = "demo_data/stopwords-ch-demo.txt",
symbol = T)
segment(text, seg4)## n ns n x n x n
## "綠黨" "桃園市" "議員" "王浩宇" "爆料" "," "指"
## x x p v n x x
## "民眾黨" "不分區" "被" "提名" "人" "蔡壁如" "、"
## x x x x x x d
## "黃瀞瑩" "," "在昨" "(" "6" ")" "才"
## v x n x x x n
## "請辭" "為領" "年終獎金" "。" "台灣" "民眾黨" "主席"
## x ns n x x v x
## "、" "台北" "市長" "柯文哲" "7" "受訪" "時則"
## zg x p n v x df
## "說" "," "按" "流程" "走" "," "不要"
## p n x r a x
## "把" "人家" "想得" "這麼" "壞" "。"
The returned object is a named character vector, i.e., the POS tags of the words are included in the names of the vectors.
Every POS tagger has its own predefined tagset. The following table lists the annotations of the POS tagset used in jiebaR:
segment(text, seg4) into a long string as shown below?
## [1] "綠黨/n 桃園市/ns 議員/n 王浩宇/x 爆料/n ,/x 指/n 民眾黨/x 不分區/x 被/p 提名/v 人/n 蔡壁如/x 、/x 黃瀞瑩/x ,/x 在昨/x (/x 6/x )/x 才/d 請辭/v 為領/x 年終獎金/n 。/x 台灣/x 民眾黨/x 主席/n 、/x 台北/ns 市長/n 柯文哲/x 7/x 受訪/v 時則/x 說/zg ,/x 按/p 流程/n 走/v ,/x 不要/df 把/p 人家/n 想得/x 這麼/r 壞/a 。/x"
7.1.6 Default Word Lists in JiebaR
You can check the dictionaries and the stopword list being used by jiebaR in your current enviroment:
# show files under `dictpath`
dir(show_dictpath())
# Check the default stop_words list
# Please change the path to your default dict path
# scan(file="/Library/Frameworks/R.framework/Versions/3.6/Resources/library/jiebaRD/dict/stop_words.utf8",
# what=character(),nlines=50,sep='\n',
# encoding='utf-8',fileEncoding='utf-8')
readLines("/Library/Frameworks/R.framework/Versions/3.6/Resources/library/jiebaRD/dict/stop_words.utf8", n = 50)7.1.7 Reminders
When we use segment() as a tokenization method in the unnest_tokens(), it is very important to specify bylines = TRUE in worker().
This setting would make sure that segment() takes a text-based vector as input and returns a list of word-based vectors of the same length as output.
NB: When bylines = FALSE, segment() returns a vector.
seg_byline_1 <- worker(bylines = T)
seg_byline_0 <- worker(bylines = F)
(text_tag_1 <- segment(text, seg_byline_1))## [[1]]
## [1] "綠黨" "桃園市" "議員" "王浩宇" "爆料" "指民眾"
## [7] "黨" "不" "分區" "被" "提名" "人"
## [13] "蔡壁如" "黃" "瀞" "瑩" "在昨" "6"
## [19] "日" "才" "請辭" "是" "為領" "年終獎金"
## [25] "台灣民眾" "黨" "主席" "台北" "市長" "柯文"
## [31] "哲" "7" "日" "受訪" "時則" "說"
## [37] "都" "是" "按" "流程" "走" "不要"
## [43] "把" "人家" "想得" "這麼" "壞"
(text_tag_0 <- segment(text, seg_byline_0))## [1] "綠黨" "桃園市" "議員" "王浩宇" "爆料" "指民眾"
## [7] "黨" "不" "分區" "被" "提名" "人"
## [13] "蔡壁如" "黃" "瀞" "瑩" "在昨" "6"
## [19] "日" "才" "請辭" "是" "為領" "年終獎金"
## [25] "台灣民眾" "黨" "主席" "台北" "市長" "柯文"
## [31] "哲" "7" "日" "受訪" "時則" "說"
## [37] "都" "是" "按" "流程" "走" "不要"
## [43] "把" "人家" "想得" "這麼" "壞"
class(text_tag_1)## [1] "list"
class(text_tag_0)## [1] "character"
7.2 Chinese Text Analytics Pipeline
In Chapter 5, we have talked about the pipeline for English texts processing, as shown below:
Figure 7.1: English Text Analytics Flowchart
For Chinese texts, the pipeline is similar.
In the following Chinese Text Analytics Flowchart (Figure 7.2), I have highlighted the steps that are crucial to Chinese processing.
- It is not recommended to use
quanteda::summary()andquanteda::kwic()directly on the Chinesecorpusobject because the word tokenization inquantedais not ideal (cf. dashed arrows in Figure 7.2). - It is recommended to use self-defined word segmenter for analysis. For processing under tidy structure framework, use own segmenter in
unnest_tokens(); for processing underquantedaframework, create thetokensobject, which is defined inquantedaas well.
Figure 7.2: Chinese Text Analytics Flowchart
It is important to note that when we specify a self-defined unnest_tokens(…,token=…) function, this function should take a character vector (i.e., a text-based vector) and return a list of character vectors (i.e., word-based vectors) of the same length.
In other words, when initializing the Chinese word segmenter, we need to specify the argument worker(…, byline = TRUE).

7.2.1 Creating a Corpus Object
- So based on our simple corpus example above, we first transform the character vector
textinto acorpusobject—text_corpus. With this, like with the English data, we can applyquanteda::summary()andquanteda::kwic()with thecorpusobject.
text_corpus <- text %>%
corpus
summary(text_corpus)kwic(text_corpus, pattern = "柯文哲")kwic(text_corpus, pattern = "柯")kwic(text_corpus, pattern = "柯文哲")?
7.2.2 Tidy Structure Framework
- We can now transform the
corpusobject into a text-based TIBBLE usingtidy(). Also, we generate an unique index for each row usingrow_number().
# a text-based tidy corpus
text_corpus_tidy <-text_corpus %>%
tidy %>%
mutate(textID = row_number())
text_corpus_tidy- For word segmentation, we initialize the
jiebarobject usingworker().
# initialize segmenter
my_seg <- worker(bylines = T,
user = "demo_data/dict-ch-user-demo.txt",
symbol=T)- Finally, we use
unnest_tokens()to tokenize the text-based TIBBLEtext_corpus_tidyinto a word-based TIBBLEtext_corpus_tidy_word. That is, texts included in thetextcolumn are tokenized into words, which are unnested into rows of thewordcolumn in the new TIBBLE.
# tokenization
text_corpus_tidy_word <- text_corpus_tidy %>%
unnest_tokens(word,
text,
token = function(x) segment(x, jiebar = my_seg))
text_corpus_tidy_word
In the above example, we specify our own tokenization function, function(x) segment(x, jiebar = my_seg).
This is called anonymous functions. It is a real function object, which just happens to have not been assigned to any symbol before being used.
You may check R language documentation for more detail on Writing Functions.
Generally functions are assigned to symbols but they don’t need to be. The value returned by the call to function is a function. If this is not given a name it is referred to as an anonymous function. Anonymous functions are most frequently used as arguments to other functions such as the apply family or outer.
7.2.3 Quanteda Framework
- Under the
quantedaframework, we can also create thetokensobject of the corpus and dokwic()search. - Most of the functions that work with
corpusobject can also work withtokensobject inquanteda.
text_tokens <- text_corpus_tidy$text %>%
segment(jiebar = my_seg) %>%
as.tokens
kwic(text_tokens,
pattern = "柯文哲")7.3 Comparing Tokenization Methods
quanteda also provides its own default word tokenization for Chinese texts. However, its default tokenization method does not allow us to add our own dictionary to the segmentation process, which renders the results less reliable.
We can compare the two results.
- we can use
quanteda::tokens()to see howquantedatokenizes Chinese texts. The function returns atokensobject.
# create TOKENS object using quanteda default
text_corpus %>%
tokens -> text_tokens_qtd- we can also use our own tokenization function
segment()and convert thelistto atokensobject usingas.tokens(). (This of course will give us the same tokenization result as we get in the earlierunnest_tokens()because we are using the same segmentermy_seg.)
# create TOKENS object manually
text_corpus %>%
segment(jiebar = my_seg) %>%
as.tokens -> text_tokens_jbNow let’s compare the two resulting tokens objects:
- These are the tokens based on self-defined segmenter:
# compare our tokenization with quanteda tokenization
text_tokens_jb[[1]]## [1] "綠黨" "桃園市" "議員" "王浩宇" "爆料" ","
## [7] "指" "民眾黨" "不分區" "被" "提名" "人"
## [13] "蔡壁如" "、" "黃瀞瑩" "," "在昨" "("
## [19] "6" ")" "日" "才" "請辭" "是"
## [25] "為領" "年終獎金" "。" "台灣" "民眾黨" "主席"
## [31] "、" "台北" "市長" "柯文哲" "7" "日"
## [37] "受訪" "時則" "說" "," "都" "是"
## [43] "按" "流程" "走" "," "不要" "把"
## [49] "人家" "想得" "這麼" "壞" "。"
- These are the tokens based on default
quantedatokenizer:
text_tokens_qtd[[1]]## [1] "綠黨" "桃園市" "議員" "王" "浩" "宇"
## [7] "爆" "料" "," "指" "民眾" "黨"
## [13] "不" "分區" "被" "提名" "人" "蔡"
## [19] "壁" "如" "、" "黃" "瀞" "瑩"
## [25] "," "在" "昨" "(" "6" ")"
## [31] "日" "才" "請辭" "是" "為" "領"
## [37] "年終獎金" "。" "台灣" "民眾" "黨主席" "、"
## [43] "台北市" "長" "柯" "文" "哲" "7"
## [49] "日" "受" "訪" "時" "則" "說"
## [55] "," "都是" "按" "流程" "走" ","
## [61] "不要" "把" "人家" "想得" "這麼" "壞"
## [67] "。"
Therefore, for linguistic analysis, I would suggest to define own Chinese word segmenter using jiebaR, which is tailored to specific tasks/corpora.
7.4 Data
In the following sections, we look at a few more case studies of Chinese text processing using the news articles collected from Apple News as our example corpus. The dataset is available in our course dropbox drive: demo_data/applenews10000.tar.gz.
(This dataset was collected by Meng-Chen Wu when he was working on his MA thesis project with me years ago. The demo data here was a random sample of the original Apple News Corpus.)
7.5 Loading Text Data
When we need to load text data from external files (e.g., txt, tar.gz files), there is a simple and powerful R package for loading texts: readtext. The main function in this package, readtext(), which takes a file or a directory name from the disk or a URL, and returns a type of data.frame that can be used directly with the corpus() constructor function in quanteda, to create a quanteda corpus object.
In other words, the output from readtext can be directly passed on to the processing in the tidy structure framework (i.e., tidytext::unnest_tokens()).
The function readtext() works on:
- text (.txt) files;
- comma-separated-value (.csv) files;
- XML formatted data;
- data from the Facebook API, in JSON format;
- data from the Twitter API, in JSON format; and
- generic JSON data.
The corpus constructor command corpus() works directly on:
- a vector of character objects, for instance that you have already loaded into the workspace using other tools;
- a data.frame containing a text column and any other document-level metadata
- the output of
readtext::readtext()
# loading the corpus
# NB: this may take some time
apple_corpus <- readtext("demo_data/applenews10000.tar.gz") %>% corpus
summary(apple_corpus, 10)7.6 quanteda::tokens() vs. jiebaR::segment()
In Chapter 4, we’ve seen that after we create a corpus object, we can apply kwic() to get the concordance lines of a particular word. At that time, we emphasized that this worked because quanteda underlyingly tokenized the texts behind the scene.
We can do the same the with Chinese texts as well:
kwic(apple_corpus, "勝率")In Section 7.3, I have made it clear that quanteda does have its own tokenization method (i.e., tokens()) for Chinese texts. It uses the tokenizer, stringi::stri_split_boundaries, which utilizes a library called ICU (International Components for Unicode) and the library uses dictionaries for segmentation of texts in Chinese.
The biggest problem is that we cannot add our own dictionary when using the default tokenization tokens() (at least I don’t know how). In other words, when we apply kwic() to apple_corpus, quanteda tokenizes the Chinese texts using its default tokenizer (i.e., tokens())and perform the keyword-in-context search.
Like we did in Section 7.3, we can compare the word segmentation results between quanteda defaults and jiebaR (with own dictionary) with our current news corpus.
To create
tokensusingjiebaR:- First we tokenize all texts in
apple_corpususingjiebaR::segment()and thejiebarinitialized with our user-defined dictionary. - Second, we convert the returned list from
segment()into atokensobject usingas.tokens().
- First we tokenize all texts in
To create
tokensusingquanteda:- We use
quantedadefaulttokens()to convert thecorpusobject intotokensobject.
- We use
# Initialize the segmenter
segmenter <- worker(user="demo_data/dict-ch-user.txt",
bylines = T,
symbol = T)
# Tokenization using jiebaR
apple_corpus %>%
segment(jiebar = segmenter) %>%
as.tokens -> apple_tokens
# Tokenization using qunateda::tokens()
apple_corpus %>%
tokens -> apple_tokens_qtdNow we can compare the two versions of word segmentation. Let’s take a look at the first document:
apple_tokens[[1]] %>% length## [1] 168
apple_tokens_qtd[[1]] %>% length## [1] 148
apple_tokens[[1]] %>% as.character## [1] "《" "蘋果" "體育" "》" "即日起" "進行" "虛擬" "賭盤"
## [9] "擂台" "," "每名" "受邀" "參賽者" "進行" "勝負" "預測"
## [17] "," "每周" "結算" "在" "周二" "公布" "," "累積"
## [25] "勝率" "前" "3" "高" "參賽者" "可" "繼續" "參賽"
## [33] "," "單周" "勝率" "最高者" "," "將" "加封" "「"
## [41] "蘋果" "波神" "」" "頭銜" "。" "註" ":" "賭盤"
## [49] "賠率" "如有" "變動" "," "以" "台灣" "運彩" "為主"
## [57] "。" "\n" "資料" "來源" ":" "NBA" "官網" "http"
## [65] ":" "/" "/" "www" "." "nba" "." "com"
## [73] "\n" "\n" "金塊" "(" "客" ")" " " "103"
## [81] ":" "92" " " "76" "人" "騎士" "(" "主"
## [89] ")" " " "88" ":" "82" " " "快艇" "活塞"
## [97] "(" "客" ")" " " "92" ":" "75" " "
## [105] "公牛" "勇士" "(" "客" ")" " " "108" ":"
## [113] "82" " " "灰熊" "熱火" "(" "客" ")" " "
## [121] "103" ":" "82" " " "灰狼" "籃網" "(" "客"
## [129] ")" " " "90" ":" "82" " " "公鹿" "溜"
## [137] "馬" "(" "客" ")" " " "111" ":" "100"
## [145] " " "馬刺" "國王" "(" "客" ")" " " "112"
## [153] ":" "102" " " "爵士" "小牛" "(" "客" ")"
## [161] " " "108" ":" "106" " " "拓荒者" "\n" "\n"
apple_tokens_qtd[[1]] %>% as.character ## [1] "《" "蘋果" "體育"
## [4] "》" "即日起" "進行"
## [7] "虛擬" "賭" "盤"
## [10] "擂台" "," "每名"
## [13] "受邀" "參賽者" "進行"
## [16] "勝負" "預測" ","
## [19] "每周" "結算" "在"
## [22] "周二" "公布" ","
## [25] "累積" "勝率" "前"
## [28] "3" "高" "參賽者"
## [31] "可" "繼續" "參賽"
## [34] "," "單" "周"
## [37] "勝率" "最高" "者"
## [40] "," "將" "加封"
## [43] "「" "蘋果" "波"
## [46] "神" "」" "頭銜"
## [49] "。" "註" ":"
## [52] "賭" "盤" "賠"
## [55] "率" "如有" "變動"
## [58] "," "以" "台灣"
## [61] "運" "彩" "為主"
## [64] "。" "資料" "來源"
## [67] ":" "NBA" "官"
## [70] "網" "http://www.nba.com" "金塊"
## [73] "(" "客" ")"
## [76] "103" ":" "92"
## [79] "76" "人" "騎士"
## [82] "(" "主" ")"
## [85] "88" ":" "82"
## [88] "快艇" "活塞" "("
## [91] "客" ")" "92"
## [94] ":" "75" "公牛"
## [97] "勇士" "(" "客"
## [100] ")" "108" ":"
## [103] "82" "灰" "熊"
## [106] "熱火" "(" "客"
## [109] ")" "103" ":"
## [112] "82" "灰" "狼"
## [115] "籃網" "(" "客"
## [118] ")" "90" ":"
## [121] "82" "公鹿" "溜"
## [124] "馬" "(" "客"
## [127] ")" "111" ":"
## [130] "100" "馬" "刺"
## [133] "國王" "(" "客"
## [136] ")" "112" ":"
## [139] "102" "爵士" "小牛"
## [142] "(" "客" ")"
## [145] "108" ":" "106"
## [148] "拓荒者"
kwic(apple_tokens, "勝率")kwic(apple_tokens_qtd, "勝率")Any significant differences in the word tokenization?
To work with the Chinese texts, if you need to utilize more advanced text-analytic functions provided by quanteda, please perform the word tokenization on the texts using your own word segmenter first and convert the object into a tokens, which can then be properly passed on to other functions in quanteda (e.g., dfm).
(In other words, for Chinese text analytics, probably corpus object is less practical; rather, creating a tokens object of your corpus might be more useful.)
In the later demonstrations, we will use our own defined segmenter for word segmentation/tokenization.
7.7 Case Study 1: Word Frequency and Wordcloud
We follow the same steps as illstrated in the above flowchart 7.2 and deal with the Chinese texts using the tidy structure framework:
- Load the corpus data using
readtext()and convert it into ancorpusobject - Create a text-based tidy structure DF
apple_corpus_tidy(i.e., a tibble) - Intialize a word segmenter using
worker() - Tokenize the text-based data frame into a word-based tidy data frame using
unnest_tokens()
# loading corpus
apple_df <- apple_corpus %>%
tidy %>%
filter(text !="") %>% #remove empty documents
mutate(doc_id = row_number()) # create doccument index# Initialize the `jiebar`
segmenter_word <- worker(user="demo_data/dict-ch-user.txt",
bylines = T,
symbol = T)# Tokenization: Word-based DF
apple_word <- apple_df %>%
unnest_tokens(output = word,
input= text,
token = function(x) segment(x, jiebar = segmenter_word)) %>%
group_by(doc_id) %>%
mutate(word_id = row_number()) %>% # create word index within each document
ungroup
apple_word %>% head(100)These tokenization results should be the same as our earlier apple_tokens:
apple_word %>%
filter(doc_id == 1) %>%
mutate(word_quanteda_tokens = apple_tokens[[1]])Creating unique indices for your data is very important. In corpus linguistic analysis, we often need to trace back to the original context where the word, phrase or sentence comes from. With all these unique indices, we can easily keep track of the sources of all tokenized linguistic units.
Also, if the metadata of the source documents are available, these unique indices would allow us to connect the tokenized linguistic units to the metadata information (e.g., genres, registers, author profiles)
With a word-based tidy DF, we can easily generate a word frequency list as well as a wordcloud to have a quick overview of the word distribution in the corpus.
stopwords_chi <- readLines("demo_data/stopwords-ch.txt")
apple_word_freq <- apple_word %>%
filter(!word %in% stopwords_chi) %>% # remove stopwords
filter(word %>% str_detect(pattern = "\\D+")) %>% # remove words consisting of digits
count(word) %>%
arrange(desc(n))
library(wordcloud2)
apple_word_freq %>%
filter(n > 400) %>%
filter(nchar(word) >=2) %>%
wordcloud2(shape = "star", size = 0.3)
7.8 Case Study 2: Patterns
In this case study, we are looking at a more complex example. In corpus linguistic analysis, we often need to extract a particular pattern from the texts. In order to retrieve the target patterns at a high accuracy rate, we often need to make use of the additional annotations provided by the corpus.
The most often-used information is the parts-of-speech tags of words. So here we demonstrate how to add POS tags information to our current tidy corpus design.
Our steps are as follows:
- Initilize
jiebarobject - Define own function to word-seg and pos-tag each text and combine all tokens,
word/tag, into a long string for each text - With the text-based
apple_df, create a new column, which includes the tokenized version of each text, usingmutate()
# initilize `jiebar`
segmenter_word_pos <- worker(type = "tag", # get pos
user = "demo_data/dict-ch-user.txt", # use own dict
symbol = T, # keep symbols
bylines = FALSE) # for `mutate()` use
# define own function
tag_text <- function(x, jiebar){
segment(x, jiebar) %>%
paste(names(.), sep="/", collapse=" ")
}
# Testing
tag_text(apple_df$text[2], segmenter_word_pos)## [1] "【/x 動/v 新聞/n ╱/x 綜合/vn 報導/n 】/x 新北市/x 一名/m 18/m 歲/zg 李姓/x 男子/n ,/x 疑因/x 女友/n 要/v 分手/v ,/x 避不見面/i 也/d 不/d 接電話/l ,/x 他/r 為/zg 見/v 女友/n 一面/m ,/x 挽回/v 感情/n ,/x 竟學/x 蜘蛛人/n 攀爬/v 鐵窗/n ,/x 欲/d 潛入/v 女友/n 位於/v 5/x 樓/n 住處/n ,/x 行經/n 2/x 樓時/x 被/p 住戶/n 發現/v ,/x 他/r 誆稱/x 「/x 撿/v 鑰匙/n 」/x 矇混過關/l ,/x 但/c 仍/zg 被/p 4/x 樓/n 住戶/n 懷疑/v 是/v 小偷/d 報案/n ,/x 最後/x 雖/zg 成功/x 進入/v 5/x 樓/n 見到/v 女友/n ,/x 仍/zg 無法挽回/i 感情/n ,/x 因/p 侵入/v 住宅/n 罪嫌/n 被/p 帶回/v 警局/x ,/x 女方/n 家屬/n 不/d 提告/x 作罷/v 。/x 警方/n 指出/v ,/x 李男為/x 挽回/v 感情/n ,/x 鋌而走險/x 攀爬/v 鐵窗/n 至/p 5/x 樓/n ,/x 其後/x 方/n 就是/d 一處/m 工地/n ,/x 萬一/x 失足/v 墜落/v ,/x 後果/n 不堪設想/i ,/x 經/zg 勸說/v 後/f ,/x 讓/v 李/nr 男/n 離去/v 。/x \n/x /x"
# apply tagger function to each text
system.time(apple_df %>%
mutate(text_tag = map_chr(text, tag_text, segmenter_word_pos)) -> apple_df_2)## user system elapsed
## 6.035 0.139 6.182
apple_df_2 %>% head7.8.1 BEI Construction
This section will show you how we can make use of the POS tags for construction analysis. I would like to illustrate their usefulness with a case study: 被 + ... Construction.
The data retrieval process is now very straighforward: we only need to create a regular expression that matches our construction and go through the word-segmented and pos-tagged texts (i.e., text_tag column in apple_df_2) to identify these matches.
In the following example, we:
- define a regular expression
\\b被/p\\s([^/]+/[^\\s]+\\s)*?[^/]+/vfor BEI-Construction, i.e., 被 + VERB - use
unnest_tokens()andstr_extract_all()to extract target patterns
# define regex patterns
pattern_bei <- "\\b被/p\\s([^/]+/[^\\s]+\\s)*?[^/]+/v"
# extract patterns from corp
apple_df_2 %>%
select(-text) %>% # `text` is the column with original raw texts
unnest_tokens(output = pat_bei,
input = text_tag,
token = function(x) str_extract_all(x, pattern=pattern_bei)) -> result_bei
result_beiPlease check Chapter 5 Parts of Speech Tagging on evaluating the quality of the data retrieved by a regular expression (i.e., precision and recall).
To have a more in-depth analysis of BEI construction, we like to automatically extract the verb used in the BEI construction.
# Extract BEI + WORD
result_bei <- result_bei %>%
mutate(VERB = str_replace(pat_bei,".+\\s([^/]+)/v$","\\1"))
result_bei# Calculate WORD frequency
require(wordcloud2)
result_bei %>%
count(VERB) %>%
mutate(n = log(n)) %>%
top_n(100, n) %>%
wordcloud2(shape="diamond",size = 0.3)
result_bei. How do we keep this information? That is, please have one column in result_bei, which shows the original texts from which the construction token is extracted.